Aerospike Health and Performance Report

Author

Aerospike TAM Team

Published

February 9, 2026

Aerospike Cluster Health Assessment

This report provides a technical analysis of the common-aerospike_va7prod cluster.

System Attribute Value
Server Version E-7.2.0.6
Node Count 3 Nodes
Active Features Batch, Index-on-flash, KVS, PIndex Query, Rack-aware, SIndex Query, Security, UDF, XDR

Executive Summary

This diagnostic evaluates the current state of the common-aerospike_va7prod environment. Findings are prioritized by impact on cluster stability.

NoteTAM Assessment Scope

Findings are based on a point-in-time snapshot. Remediation should be tested in a staging environment before production deployment.

Cluster Status Overview

WarningConfig Symmetry

Detected 31 configuration drifts across the cluster.

WarningDelete Not Found

Detected 734,214,682 ‘Delete Not Found’ events across 3 nodes.

Performance and Utilization

Disk Usage % by Node

Client Connections

Observations and Remediation

1.b: ENA Support Check

ENA Telemetry Missing: OS-level statistics were not found in this bundle.

Recommendation: To retrieve this data, run ‘collectinfo’ as root or use ‘asadm –lsmod –ethtool’. Manually verify with: ‘ethtool -i eth0’.


1.c: Version Consistency

Telemetry not yet ingested.

Recommendation: Review telemetry.


3.a: Config Symmetry

Detected 31 configuration drifts across the cluster.

Recommendation: Check the Technical Details section to identify which specific parameters (e.g. memory, timeouts) differ.


3.b: Config Drift

The static aerospike.conf file was not found in the collectinfo bundle.

Recommendation: Cannot perform drift analysis (Runtime vs. Static). To enable this check in the future, run: ‘asadm -e “collectinfo –cf /etc/aerospike/aerospike.conf”’


4.b: Read Not Found

Detected 10,590,009,790 ‘Read Not Found’ events. This is often normal for application cache-miss workflows.

Recommendation: If the application expects all records to exist, investigate potential expiration or eviction issues.


4.c: Delete Not Found

Detected 734,214,682 ‘Delete Not Found’ events across 3 nodes.

Recommendation: This suggests the application is attempting to delete records that do not exist (Blind Deletes). Review application logic.


Appendix: All Tests Performed

Check Name Status
1.a: Service Error Skew ✅ PASS
1.b: ENA Support Check ⚠️ INFO
1.c: Version Consistency ⚠️ INFO
2.a: SIndex on Flash ✅ PASS
2.b: Sprig Limit Warning ✅ PASS
2.c: Storage Deadlock Risk ✅ PASS
2.d: Disk HWM Check ✅ PASS
2.e: Memory HWM Check ✅ PASS
3.a: Config Symmetry ⚠️ WARNING
3.b: Config Drift ⚠️ ⚠️ DATA MISSING
4.a: Hot Key Detection ✅ PASS
4.b: Read Not Found ⚠️ INFO
4.c: Delete Not Found ⚠️ WARNING

Aerospike Health Analyzer | Version: 1.3.0 | Generated: 2026-02-09 15:32